Allow CI Workflow Run

• approve CI run for commit: 69347c9

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

Actually, bunx create-next-app works perfectly fine, as does bun create next-app. they are identical in behaviour

This is to be expected, as they are supposed to be the bun equivalents of npx create-X and npm create X, respectively.

UPDATE: output for both commands

@abdoufma I don't quite understand what the issue is, and I've tried bunx create-next-app with bash, zsh, and PowerShell; it works fine. But for cases with terminals like Command Prompt, it will give an error.
However, for the bunx create next-app command, it might work well on all OS and terminals. That's why I created a PR providing a flexible solution so that the command can run on everything.

It’s peculiar that bunx create next-app works for you at all, since It’s the only one that doesn’t for me. (bun create X works, bunx create X doesn’t)

That's not too surprising, as It’s not documented anywhere that it should work; bunx create next-app essentially looks for the create package and attempts to execute its bin script, passing next-app as an argument (which should fail).

Both bunx create-next-app and bun create next-app worked as expected on linux and macOS (using both zsh and bash), and on Windows 10/11 (using both CMD and powershell)

bunx create next-app doesn't work anywhere.

Results of executing all three command on windows powershell and CMD:

Thanks for the re-clarifications. It's likely a separate issue causing bunx to not work, but since the docs primarily use bun create, we'll stick with that.

@samcx Agreed. A command supported by all package managers is prefered.
In that case however, shouldn't the npm instruction be similarly switched to npm create next-app ? 🤔

Thanks for the explanation; now I understand. Sorry if I caused any confusion. I thought I could help by providing this PR, and the developers approved it. I just thought it could help everyone. I didn't expect there would be a debate about this. I'm not an expert in anything, and thanks for clarifying; now I get it. Thank you, developers, for reviewing this PR.

@abdoufma I'm not seeing npm create being mentioned, but I do still see npx → https://docs.npmjs.com/cli/v10/commands/npx.

@samcx Admittedly, finding the relevant documentation wasn't easy at first, but npm create is essentially an alias for npm init which in turn calls npm exec

And as per npm init's docs:

npm init <initializer> can be used to set up a new or existing npm package.
initializer in this case is an npm package named create-<initializer>, which will be installed by npm-exec, and then have its main bin executed -- presumably creating or updating package.json and running any other initialization-related operations.

In other words: npm create X, npm init X, npm exec create-X, and npx create-X are all different ways to achieve the same outcome.